Methods for providing regulation compliant privacy and related apparatuses

ABSTRACT

A method of operating a network device in a serving network for providing regulation compliant privacy in a communications network is provided. Operations of such methods include obtaining a concealed subscription identifier from a user equipment, UE, that is associated with a home network, HN, obtaining a permanent subscription identifier that is associated with the concealed subscription identifier from the HN, determining whether the concealed subscription identifier from the UE corresponds to the permanent subscription identifier from the HN, and responsive to determining that the concealed subscription identifier from the UE corresponds to the permanent subscription identifier from the HN, performing further operations to provide service to the UE.

RELATED APPLICATION

The present application claims the benefit of and priority to U.S.Provisional Patent Application No. 62/794,940 filed Jan. 21, 2019,entitled “METHODS FOR PROVIDING REGULATION COMPLIANT PRIVACY AND RELATEDAPPARATUSES” the disclosure of which is hereby incorporated herein byreference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to wireless communicationssystems and, more particularly, to supervised regulation complaintprivacy in a wireless network.

BACKGROUND

5G is a next generation of mobile networks developed by a standarddeveloping organization called the 3GPP. The earlier generations ofmobile networks were called 4G/LTE, 3G/UMTS, and 2G/GSM.

A 5G network is maintained and its services are offered by the so-calledMobile Network Operators (MNOs). MNOs are distinguishable from eachother by two types of codes, namely the Mobile Country Code (MCC) andthe Mobile Network Code (MNC).

To use a particular 5G network offered by a particular MNO, users arerequired to have a sort of contractual relationship with that MNO. Thatrelationship may be generally called the subscription. In cases when theuser lacks a subscription to some particular MNO (e.g., in a roamingscenario), the relationship is achieved by roaming agreements betweenthe MNO where the user has a subscription, i.e., the user's Home Network(HN) and the MNO that the user is being served, i.e., the VisitedNetwork (VN).

Each subscription in a MNO's 5G network is identified by a uniquelong-term identifier called the Subscription Permanent Identifier(SUPI). Users wirelessly access a 5G network over-the-air using wirelessdevice known as User Equipment (UE). Before providing any service, a 5Gnetwork needs to identify a user, i.e., the user's subscription, behinda UE. For this purpose of identification, UEs in earlier generation ofmobile networks (4G, 3G, and 2G) would send users' unique long-termidentifier over-the-air. This raised a potential privacy issue becauseusers could be tracked or identified by any unauthorized entity capableof intercepting message or acting as man-in-the-middle over-the-air.

However, in a 5G network, the MNO has an ability to offer better privacyto its users so that their unique long-term identifiers (i.e., SUPIs)are not visible over-the-air. That ability comes from a mechanism inwhich UEs, instead of sending SUPIs, calculate and send concealedidentifiers over-the-air, which is called the Subscription ConcealedIdentifier (SUCI). The MNO may make available to UEs all informationthat are necessary for the calculation of SUCI.

Without a loss of generality, the SUPI and the SUCI formats are outlinedbelow.

The SUPI contains the following parts (separated by ∥): SUPI type∥SUPIvalue, where the SUPI value can be either of type IMSI or networkspecific identifier (also sometimes called as network access identifieror NAI). In either case, the SUPI value consists of a home networkidentifier and a subscription identifier. The subscription identifier iswhat is concealed in the SUCI.

The SUCI contains the following parts (separated by ∥): SUPI type∥HomeNetwork Identifier∥other parameters∥Concealed subscription identifier.

If the SUPI is of type IMSI, the Home Network identifier consists of anMobile Country Code (MCC) and Mobile Network Code (MNC) and thesubscription identifier is called Mobile Subscription IdentificationNumber (MSIN). If the SUPI is of type network specific identifier, theHome Network Identifier is generally represented by so-called “realm”,and the subscription identifier is generally represented by so-called“username”, i.e., SUPI would look like username@realm. The exactdefinitions of SUPI can be found in 3GPP TS 23.003 V.15.6.0.

3GPP 33.501 V.15.3.0 specifies that for SUPIs containing IMSI, the SUCIhas following fields: the SUPI Type as defined in TS 23.003 V.15.6.0identifies the type of the SUPI concealed in the SUCI; the Home NetworkIdentifier is set to the MCC and MNC of the IMSI as specified in 23.003V.15.6.0; the Routing Indicator as specified in TS 23.003 V.15.6.0; theProtection Scheme Identifier as specified in Annex C of 3GPP TS 33.501V.15.3.0; the Home Network Public Key Identifier as specified in 3GPP TS33.501 V.15.3.0 and detailed in TS 23.003 V.15.6.0; and the SchemeOutput as specified in this document and detailed in TS 23.003 V.15.6.0.

Further, 3GPP 33.501 V.15.3.0 specifies that for SUPIs containingNetwork Specific Identifier, the SUCI in NAI format has followingfields: the realm part of the SUCI is set to the realm part of the SUPI;and the username part of the SUCI is formatted as specified in TS 23.003V.15.6.0 using the SUPI Type, Routing Indicator, the Protection SchemeIdentifier, the Home Network Public Key Identifier and the SchemeOutput.

Potential Problems with Existing Solutions

The following explanation of potential problems with existing solutionsis a present realization as part of the present disclosure and is not tobe construed as previously known by others.

A high level sequence diagram showing message flow comprising the SUCIis shown in FIG. 1, which is a data flow diagram illustrating a UEregistration using SUCI. Referring to FIG. 1, in operation 1, the UEconnects to a gNB over-the-air (the gNB being a 5G base station and partof the 5G Radio Access Network (RAN)) and sends a Registration Requestmessage which comprises a SUCI calculated by the UE. In operation 2, thegNB forwards the received Registration Request message to a core networknode. We denote that core network node as an Access and MobilityManagement Function (AMF) or Security Anchor Function (SEAF)interchangeably. The gNB and AMF/SEAF are collectively denoted asServing Network (SN). The SEAF further locates the Authentication ServerFunction (AUSF). The SEAF then creates and sends to the AUSF. Inoperation 3, a 5G Authentication Information Request (AIR) that amongother information contains the received SUCI. The AUSF then contacts theUnified Data Management (UDM) or Subscription Identifier De-concealingFunction (SIDF) function in operation 4.

The AUSF and UDFM/SIDF are collectively denoted as Home Network (HN).Note that the in case of roaming the SN and the HN belong to differentMNOs while otherwise both the SN and HN belong to the same MNO.

Also note that registration involves more steps than these messages butthis gives an overview of how the SUCI travels over the network.

Problems with existing solutions include that when the SUPI (denoting along-term identifier) is concealed between a UE and its HN, all thenetwork functions between them do not know the SUPI, including the SN.Therefore, it is challenging for the SN to fulfill its lawfulinterception obligations. This may not be acceptable because the SN mustbe able to fulfill its lawful interception obligations irrespective ofwhether the UEs in its network are roaming or not.

SUMMARY

Some embodiments are directed to methods of operating a network devicein a serving network, SN, for providing regulation compliant privacy ina communications network. Such methods include operations of obtaining aconcealed subscription identifier from a user equipment, UE, that isassociated with a home network, HN, obtaining a permanent subscriptionidentifier that is associated with the concealed subscription identifierfrom the HN, determining whether the concealed subscription identifierfrom the UE corresponds to the permanent subscription identifier fromthe HN, and, responsive to determining that the concealed subscriptionidentifier from the UE corresponds to the permanent subscriptionidentifier from the HN, performing further operations to provide serviceto the UE.

In some embodiments, operations include, responsive to determining thatthe concealed subscription identifier from the UE does not correspond tothe permanent subscription identifier from the HN, denying service tothe UE.

Some embodiments provide that denying the service to the UE includes atleast one of rejecting a registration of the UE with the SN, logging anevent corresponding to the concealed subscription identifier notcorresponding to the permanent subscription identifier, notifying a lawenforcement organization, and notifying the UE.

In some embodiments, the concealed subscription identifier includes aSUCI that is calculated by the UE based on information provided by theHN.

Some embodiments provide that the permanent subscription identifierincludes a SUPI.

In some embodiments, the SUPI includes an International MobileSubscription Identifier, IMSI, or a network specific identifier.

Some embodiments provide that the concealed subscription identifierconceals the permanent subscription identifier.

In some embodiments, obtaining the concealed subscription identifierincludes obtaining a first home network identifier corresponding to theUE having a first value and a second home network identifiercorresponding to the HN having a second value.

In some embodiments, obtaining the first home network identifierincludes obtaining a mobile country code, MCC, having a first MCC valueand a mobile network code, MNC, having a first MNC value, obtaining thesecond home network identifier includes obtaining an MCC having a secondMCC value and the MNC having the second MNC value, and determining thatthe first home network identifier corresponds to the second home networkidentifier includes determining that the first MCC value equals thesecond MCC value and that the first MNC value equals the second MNCvalue.

Some embodiments provide that the first home network identifier includesa first format and the second home network identifier includes a secondformat that is different from the first format and, responsive todetermining that the first format and the second format comprise a samerealm, operations provide service to the UE.

In some embodiments, obtaining the concealed subscription identifierincludes obtaining a mobile country code, MCC, having a first MCC valueand a mobile network code, MNC, having a first MNC value, obtaining thepermanent subscription identifier includes obtaining the MCC having asecond MCC value and the MNC having the second MNC value, anddetermining that the concealed subscription identifier corresponds tothe permanent subscription identifier includes determining that thefirst MCC value equals the second MCC value and that the first MNC valueequals the second MNC value.

Some embodiments provide that performing the subscription bindingincludes performing the subscription binding using the second MCC valueand the second MNC value.

Some embodiments include determining if a SUPI type is received from theUE and the HN.

In some embodiments, the concealed subscription identifier includes afirst type and the permanent subscription identifier includes a secondtype that is different from the first type. Some embodiments providethat determining that the concealed subscription identifier correspondsto the permanent subscription identifier includes determining that thefirst MCC value in the first type equals the second MCC value in thesecond type and that the first MNC value in the first type equals thesecond MNC value in the second type.

In some embodiments, determining that the concealed subscriptionidentifier corresponds to the permanent subscription identifier includesdetermining that the first MCC value in the first type is different fromthe second MCC value in the second type and that the first MNC value inthe first type is different form the second MNC value in the secondtype.

Some embodiments provide that the SN generates an indication to deny theservice responsive the first type being different from the second type.In some embodiments, the first type includes a first format that definesa realm and the second type includes a second format type that definesthe realm. In some embodiments, the operations are provided to the UE.

In some embodiments, the concealed subscription identifier includes afirst type and the permanent subscription identifier includes the firsttype. Some embodiments include determining that the first type is IMSIand, responsive to determining that the first type is IMSI, determiningthat the MCC/MNC are the same.

Some embodiments provide determining that the first type is NSI and,responsive to determining that the first type is NSI, determining thatthe MCC/MNC includes a same realm.

Some embodiments include transmitting (700) the concealed subscriptionidentifier that is received from the UE to the HN.

Some embodiments described herein are directed to methods of operating amobile terminal for providing regulation compliant privacy in acommunications network. Operations according to such methods includetransmitting a concealed subscription identifier to a service network.In some embodiments, the concealed subscription identifier includes atleast a first home network identifier. Operations include using a SUPIwith at least the first home network identifier in binding.

Some embodiments provide that the concealed subscription identifierincludes a first MCC value and a first MNC value.

In some embodiments, the concealed subscription identifier conceals apermanent subscription identifier.

In some embodiments, the concealed subscription identifier includes anIMSI type.

Some embodiments provide that the concealed subscription identifierincludes a network access identifier, NAI.

In some embodiments, the mobile terminal uses the permanent subscriptionidentifier that is concealed in the concealed subscription identifier toperform a SUPI binding.

Some embodiments described herein are direct to a mobile terminal thatincludes at least one processor and at least one memory connected to theat least one processor. The memory stores program code that is executedby the at least one processor to perform operations includingtransmitting a concealed subscription identifier to a service network.In some embodiments, the concealed subscription identifier includes atleast a first home network identifier. Operations include using a SUPIwith at least the first home network identifier in binding.

In some embodiments, the concealed subscription identifier includes afirst MCC value and a first MNC value.

Some embodiments provide that the concealed subscription identifierconceals a permanent subscription identifier.

In some embodiments, the concealed subscription identifier includes anIMSI type.

In some embodiments, the concealed subscription identifier includes anetwork access identifier, NAI.

Some embodiments provide that the mobile terminal uses the permanentsubscription identifier that is concealed in the concealed subscriptionidentifier to perform a SUPI binding.

Embodiments here herein are directed to a computer program product thatincludes a non-transitory computer readable medium storing program codeconfigured for execution by a processor disclosed herein and configuredto perform operations described herein to provide regulation compliantprivacy in a communications network.

Embodiments herein are directed to a computer program for providingregulation compliant privacy in a communications network that, whenexecuted, performs operations described herein.

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the disclosure and are incorporated in and constitute apart of this application, illustrate certain non-limiting embodiments ofinventive concepts.

FIG. 1 is a data flow diagram illustrating a UE registration using SUCI;

FIG. 2 is a data flow diagram illustrating a procedure for SUPI bindingaccording to some embodiments.

FIG. 3, which is a data flow diagram illustrating operations in whichthe SUPI does not match the SUCI according to some embodiments.

FIG. 4 is a data flow diagram illustrating operations that include anauthentication of parameters corresponding to the SUPI and SUCIaccording to some embodiments.

FIGS. 5-7 are flowcharts of operations that may be performed inaccordance with some embodiments of the present disclosure.

FIG. 8 is a block diagram of elements of a mobile terminal that areconfigured according to some embodiments of the present disclosure;

FIG. 9 is a block diagram of elements of a network node that areconfigured according to some embodiments of the present disclosure;

FIG. 10 is a block diagram of a wireless network in accordance with someembodiments of the present disclosure;

FIG. 11 is a block diagram of a user equipment or other terminal inaccordance with some embodiments of the present disclosure;

FIG. 12 is a block diagram of a virtualization environment in accordancewith some embodiments of the present disclosure;

FIG. 13 is a block diagram of a telecommunication network connected viaan intermediate network to a host computer in accordance with someembodiments of the present disclosure;

FIG. 14 is a block diagram of a host computer communicating via a basestation with a user equipment user equipment or other terminal over apartially wireless connection in accordance with some embodiments of thepresent disclosure;

FIG. 15 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipmentuser equipment or other terminal in accordance with some embodiments ofthe present disclosure;

FIG. 16 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipmentuser equipment or other terminal in accordance with some embodiments ofthe present disclosure;

FIG. 17 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipmentuser equipment or other terminal in accordance with some embodiments ofthe present disclosure; and

FIG. 18 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipmentuser equipment or other terminal in accordance with some embodiments ofthe present disclosure.

DETAILED DESCRIPTION

Inventive concepts will now be described more fully hereinafter withreference to the accompanying drawings, in which examples of embodimentsof inventive concepts are shown. Inventive concepts may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Rather, these embodiments areprovided so that this disclosure will be thorough and complete, and willfully convey the scope of present inventive concepts to those skilled inthe art. It should also be noted that these embodiments are not mutuallyexclusive. Components from one embodiment may be tacitly assumed to bepresent/used in another embodiment.

The following description presents various embodiments of the disclosedsubject matter. These embodiments are presented as teaching examples andare not to be construed as limiting the scope of the disclosed subjectmatter. For example, certain details of the described embodiments may bemodified, omitted, or expanded upon without departing from the scope ofthe described subject matter. The term “terminal” is used in anon-limiting manner and, as explained below, can refer to any type ofradio communication terminal. The term “terminal” herein may beinterchangeable replaced with the term “radio terminal,” “radiocommunication terminal,” “radio device,” or “user equipment (UE).”

Further discussion of potential problems provides that one potentialsolution is that the HN indiscriminately provides the SUPI (for allSUCIs served by the SN) to the SN. While this solution may provide animportant aspect in fulfilling LI obligation, this solution is notsufficient on its own because the SN does not have any reliableverification that the HN provided the real or genuine SUPI. Therefore,the HN sending the SUPI to the SN may be necessary but is insufficient.

An additional solution may be that the SN verifies if the SUPI sent bythe HN actually belongs to the UE that the SN is serving. The SN coulduse variety of mechanisms for such verification, e.g., calculating SUCIby encrypting the SUPI sent by the HN and comparing the calculated SUCIwith the SUCI previously sent by the UE, obtaining an additionalcommitment value from the UE, obtaining another commitment-opener valuefrom the HN, and verifying that the commitment-opener can verify thecommitment, calculating an expected response by using the SUPI sent bythe HN, challenging the UE to send a response, and comparing theresponse sent by the UE with the calculated expected response, usingSUPI sent by the HN in calculation of security keys so that if the UEuses different value, the communication breaks, etc.

While some sort of verification by the SN may be yet another importantaspect in fulfilling LI obligation, different sorts of above-mentionedverification may have different properties and complexities. Ultimately,3GPP chose the last one of the above-mentioned mechanisms, i.e., usingSUPI in calculation of security key. This chosen mechanism may includethe SUPI in the calculation of keys used for communication. Using thismechanism, the keys used by the SN and the UE will not match if the SNhas received the incorrect SUPI from the HN. If the UE and the SN havedifferent keys they will not be able to communicate as they willdisregard messages protected with an incorrect key. The chosen mechanismis described in Clause 6.1.3.1 for EAP-AKA′ and Clause 6.1.3.2 for5G-AKA in 3GPP TS 33.501 V15.3.0. The inclusion of SUPI is specified inAnnex A.7 of 3GP TS 33.501 V15.3.0. Furthermore, there is discussionregarding whether or not to include the whole SUPI in the calculation ofsecurity key. Some have suggested not to include the SUPI type part ofthe SUPI into the calculation of the security key, and only use the SUPIvalue as input. An argument to exclude the SUPI type is for simplicity.There are also other suggestions to include the SUPI type part of theSUPI into the calculation of the security key. One reason to include itmay be to ensure the binding between the SUPI received from the UE andfrom the HN.

While the above-mentioned mechanism may work, and whether or not thewhole SUPI is used in calculation of security key, it still may not besufficient for completely fulfilling the lawful interception (LI)obligation because there may not be any mechanism to link the SUCIreceived by the SN from the UE to the SUPI received by the SN from theHN. It may be a challenge for the SN to have that linkage. And withoutsuch linkage, LI obligation fulfillment is questionable, which may beproblematic.

In response to the above-described challenges, some embodiments hereinare directed to enabling a network to fulfill its lawful interception(LI) obligation by ensuring that the subscription that was identified isthe same as the one that gets the service. Such embodiments may providea reliable LI obligation fulfillment.

As explained above, with the concealment of the SUPI between the UE andthe HN, it may be challenging for the SN to fulfill its lawfulinterception (LI) obligation because there may be no mechanism thatenables the SN to link the SUCI received from the UE to the SUPIreceived from the HN. Accordingly, some embodiments herein may include aSUPI that is of type IMSI. Further, embodiments may be discussed interms of MCC and MNC, however, such terms are merely example terms andthe inventive concept is not so limited. As such, embodiments areapplicable to fields/parameters/properties of SUCI and SUPI in general.Further, embodiments are not limited to a type IMSI SUPI. For example,embodiments are equally applicable to the SUPI of type network specificidentifier. For example, in addition to checking MCC and MNC fields, theSN may check other fields like the realm part of a SUPI of type NetworkSpecific Identifier, SUPI Type etc.

Reference is now made to FIG. 2, which is a data flow diagramillustrating the procedure for SUPI binding according to someembodiments. In some embodiments, in operation 1 the UE sends the SUCIto the SN. In this example, the home network identifier consists of anMCC and a MNC, with values MCC_1 and MNC_1. According to operation 2,the SN forwards the received SUCI to the HN unmodified. Operation 3provides that the HN converts the SUCI and returns the SUPI to the SN.The SUPI contains the same MCC_1, MNC_1 as the SUCI. In operation 4, theSN uses the SUPI (part of, or complete, pending ongoing discussion) asinput to a calculation of the security key. Operation 5 provides thatthe UE uses the SUPI stored locally to derive the security key. If thelocal SUPI matches the SUPI in the SN, then the binding is successful,as illustrated in operation 6.

In some embodiments, the SUPI that is received from the HN may not matchthe SUCI that is provided by the UE. Reference is now made to FIG. 3,which is a data flow diagram illustrating operations in which the SUPIdoes not match the SUCI according to some embodiments. Operation 1illustrates that the UE sends the SUCI to the SN. In this example, thehome network identifier consists of an MCC and a MNC, with values MCC_1and MNC_1. In operation 2, the SN forwards the received SUCI to the HNunmodified. In operation 3, the HN converts the SUCI and returns theSUPI to the SN. In this example, the HN returns the values MCC_2 andMNC_2. In operation 4, the SN uses the SUPI (part of, or complete,pending ongoing discussion) as input to the calculations of the securitykey. In operation 5, the UE uses the SUPI stored locally to derive thesecurity key. Since the UE will use a SUPI with the values MCC_1 andMNC_1, the UE and SN will not calculate the same key, as illustrated inoperation 6.

Reference is now made to FIG. 4, which is a data flow diagramillustrating operations that include an authentication of parameterscorresponding to the SUPI and SUCI according to some embodiments.Operations include operation 1, in which the UE sends the SUCI to theSN. In this example, the home network identifier consists of an MCC anda MNC, having values MCC_1 and MNC_1, respectively. Operation 2 providesthat the SN forwards the received SUCI to the HN in an unmodified state.In operation 3, the HN converts the SUCI and returns the SUPI to the SN.In this example, the HN returns the values MCC_x and MNC_x. In operation4, the SN verifies that the SUPI parameters that were received from theHN matches the SUPI parameters received form the UE. Examples ofparameters are MCC, MNC and/or SUPI type among others. If the parametersdo not match, the SN shall not provide service to the UE and thefollowing operations may not be performed. In some embodiments, the SNmay send an error or reject message to the UE. Some embodiments providethat the SN may inform HN of the error condition. In some embodiments,the SN may log the error condition, generate a report, and/or inform lawenforcement agencies, among others.

Some embodiments provide that a similar condition may result if the samevalues in SUPI are provided as different types. For example, conditionsin which the same subscription information is contained in SUPIcontaining IMSI or SUPI containing Network Specific Identifier (NSI).For example, #1 and #2 below could be arguable considered to be same. Insuch embodiments, the matching function corresponding to operation 4will still verify that the values are the same regardless of SUPI type.For example, in example below #1, and #2 both have 123 and 45 for HomeNetwork Identifier, and 6789100000 for subscription identifier.

-   -   1. SUPI Type (IMSI)∥MCC (123)∥MNC (45)∥MSIN (6789100000)    -   2. SUPI Type (NSI)∥username (6789100000) @ realm (MCC (123).        (MNC (45). com)

In operation 5, the SN uses part or all of the SUPI as input to thecalculations of the security key. In operation 6, the UE uses the SUPIstored locally to derive the security key. If the local SUPI matches theSUPI in the SN, the binding may be identified as successful.

These and other related operations now be described in the context ofthe operational flowcharts of FIGS. 5-7 that may be performed by amobile terminal.

Reference is now made to FIG. 5, which illustrates operations that maybe performed by a network device. Operations may include obtaining aconcealed subscription identifier from a user equipment, UE (block 500).In some embodiments, the UE is associated with a home network, HN. Theconcealed subscription identifier is transmitted to the HN (block 502).

A permanent subscription identifier is obtained from the HN (block 504).Operations include determining whether the concealed subscriptionidentifier from the UE corresponds to the permanent subscriptionidentifier from the HN (block 506). I response to determining that theconcealed subscription identifier from the UE corresponds to thepermanent subscription identifier from the HN, operations includeperforming further operations to provide service to the UE (block 508).In response to determining that the concealed subscription identifierfrom the UE does not correspond to the permanent subscription identifierfrom the HN, operations include denying service to the UE (block 510).

In some embodiments, the concealed subscription identifier comprises aSUCI that is calculated by the UE based on information provided by theHN. Some embodiments provide that the permanent subscription identifiercomprises a SUPI.

In some embodiments, the SUPI comprises an International MobileSubscription Identifier, IMSI, or a network specific identifier. Someembodiments provide that the concealed subscription identifier concealsthe permanent subscription identifier.

In some embodiments, obtaining the concealed subscription identifiercomprises obtaining a mobile country code, MCC, having a first MCC valueand a mobile network code, MNC, having a first MNC value and obtainingthe permanent subscription identifier comprises obtaining the MCC havinga second MCC value and the MNC having the second MNC value. Someembodiments provide that determining that the concealed subscriptionidentifier corresponds to the permanent subscription identifiercomprises determining that the first MCC value equals the second MCCvalue and that the first MNC value equals the second MNC value.

In some embodiments, performing the subscription binding comprisesperforming the subscription binding using the second MCC value and thesecond MNC value. In some embodiments, subscription binding in the UE isbased on the first MCC value and the first MNC value.

Some embodiments provide that determining whether the concealedsubscription identifier corresponds to the permanent subscriptionidentifier comprises generating a security key using at least a portionof the permanent subscription identifier for comparison to a securitykey that is generated by the UE using the permanent subscriptionidentifier that is stored on the UE.

Reference is now made to FIG. 6, which illustrates operations that maybe performed for denying the service to the UE according to someembodiments. Operations may include rejecting service for the UE (block600), logging an event corresponding to the concealed subscriptionidentifier not corresponding to the permanent subscription identifier(block 602), notifying a law enforcement organization (block 604, and/ornotifying the UE (block 606).

Reference is now made to FIG. 7, which illustrates operations that maybe performed by a mobile terminal according to some embodiments.Operations may include transmitting a concealed subscription identifierto a service network (block 700). In some embodiments, the concealedsubscription identifier includes at least a first home networkidentifier. In some embodiments, the concealed subscription identifierincludes a first MCC value and a first MNC value. Operations furtherinclude using a SUPI with at least the first home network identifier(block 702). A mobile terminal security key may be generated using apermanent subscription identifier that is stored on the mobile terminal.Operations may include performing a permanent subscription identifierbinding. In some embodiments, the binding is performed with the servicenetwork based on the mobile terminal security key matching a servicenetwork generated security key that is based on a second MCC value and asecond MNC value at the service network.

FIG. 8 is a block diagram illustrating a mobile terminal 106 that isconfigured according to some embodiments. The mobile terminal 106 caninclude, without limitation, a wireless terminal, a wirelesscommunication device, a wireless communication terminal, a terminalnode/UE/device, etc. The mobile terminal 106 includes a RF front-end 830comprising one or more power amplifiers the transmit and receive throughantennas of an antenna array 840 to provide uplink and downlink radiocommunications with a radio network node (e.g., a base station, eNB,gNB, etc.) of a telecommunications network. Instead of or in addition tothe RF front-end 830, the mobile terminal 106 may include a lightreception front-end configured to receive light signaling such from aLight WiFi AP. Mobile terminal 106 further includes a processor circuit810 (also referred to as a processor) coupled to the RF front end 830and a memory circuit 820 (also referred to as memory). The memory 820stores computer readable program code that when executed by theprocessor 810 causes the processor 810 to perform operations accordingto embodiments disclosed herein.

FIG. 9 is a block diagram illustrating a network node 900 (e.g., a basestation, eNB, gNB, etc.) of a telecommunications network. The networknode 900 includes a processor circuit 904 (also referred to as aprocessor), a memory circuit 906 (also referred to as memory), and anetwork interface 902 (e.g., wired network interface and/or wirelessnetwork interface) configured to communicate with other network nodes.The network node 900 may be configured as a radio network nodecontaining a RF front-end and/or a light signaling front-end with one ormore power amplifiers 908 that transmit and receive through antennas ofan antenna array 910. The memory 906 stores computer readable programcode that when executed by the processor 904 causes the processor 904 toperform operations according to embodiments disclosed herein.

The following are certain enumerated embodiments further illustratingvarious aspects of the disclosed subject matter.

Embodiment 1. A method of operating a network device in a servingnetwork for providing regulation compliant privacy in a communicationsnetwork, the method comprising:

obtaining a concealed subscription identifier from a user equipment, UE,that is associated with a home network;

obtaining a permanent subscription identifier that is associated withthe concealed subscription identifier from the home network, HN;

determining whether the concealed subscription identifier from the UEcorresponds to the permanent subscription identifier from the HN; and

responsive to determining that the concealed subscription identifierfrom the UE corresponds to the permanent subscription identifier fromthe HN, performing further operations to provide service to the UE.

Embodiment 2. The method of embodiment 1, further comprising, responsiveto determining that the concealed subscription identifier from the UEdoes not correspond to the permanent subscription identifier from theHN, denying service to the UE.

Embodiment 3. The method of embodiment 2, wherein denying the service tothe UE comprises at least one of rejecting a registration of the UE witha serving network, logging an event corresponding to the concealedsubscription identifier not corresponding to the permanent subscriptionidentifier, notifying a law enforcement organization, and notifying theUE.

Embodiment 4. The method of any of embodiments 1-3, wherein theconcealed subscription identifier comprises a SUCI that is calculated bythe UE based on information provided by the HN.

Embodiment 5. The method of any of embodiments 1-4, wherein thepermanent subscription identifier comprises a SUPI.

Embodiment 6. The method of any of embodiments 1-5, wherein the SUPIcomprises an International Mobile Subscription Identifier, IMSI, or anetwork specific identifier.

Embodiment 7. The method of any of embodiments 1-6, wherein theconcealed subscription identifier conceals the permanent subscriptionidentifier.

Embodiment 8. The method of any of embodiments 1-7, wherein obtainingthe concealed subscription identifier comprises obtaining a mobilecountry code, MCC, having a first MCC value and a mobile network code,MNC, having a first MNC value,

wherein obtaining the permanent subscription identifier comprisesobtaining the MCC having a second MCC value and the MNC having thesecond MNC value, and

wherein determining that the concealed subscription identifiercorresponds to the permanent subscription identifier comprisesdetermining that the first MCC value equals the second MCC value andthat the first MNC value equals the second MNC value.

Embodiment 9. The method of embodiment 8, wherein performing thesubscription binding comprises performing the subscription binding usingthe second MCC value and the second MNC value.

Embodiment 10. The method of any of embodiments 8-9, further comprisingdetermining if a SUPI type is received from the UE and the HN.

Embodiment 11. The method of embodiment 10, wherein the concealedsubscription identifier comprises a first type and the permanentsubscription identifier comprises a second type that is different fromthe first type.

Embodiment 12. The method of embodiment 11, wherein the determining thatthe concealed subscription identifier corresponds to the permanentsubscription identifier comprises determining that the first MCC valuein the first type equals the second MCC value in the second type andthat the first MNC value in the first type equals the second MNC valuein the second type.

Embodiment 13. The method of any of embodiments 1-12, further comprisingtransmitting the concealed subscription identifier that is received fromthe UE to the HN.

Embodiment 14. A computer program product comprising:

a non-transitory computer readable medium storing program codeconfigured for execution by a processor of a network device to cause theprocessor to perform operations for providing regulation compliantprivacy in a communications network according to embodiments 1-13.

Embodiment 15. A computer program for providing regulation compliantprivacy in a communications network that, when executed, performsoperations according to embodiments 1-13.

Embodiment 16. A network device in a communications network comprising:

at least one processor;

at least one memory connected to the at least one processor and storingprogram code that is executed by the at least one processor to performoperations comprising:

obtaining a concealed subscription identifier from a user equipment, UE,that is associated with a home network;

obtaining a permanent subscription identifier that is associated withthe concealed subscription identifier from the home network, HN;

determining whether the concealed subscription identifier from the UEcorresponds to the permanent subscription identifier from the HN; and

responsive to determining that the concealed subscription identifierfrom the UE corresponds to the permanent subscription identifier fromthe HN, performing further operations to provide service to the UE.

Embodiment 17. The network device of embodiment 16, the operationsfurther comprising, responsive to determining that the concealedsubscription identifier from the UE does not correspond to the permanentsubscription identifier from the HN, denying service to the UE.

Embodiment 18. The network device of embodiment 17, wherein denying theservice to the UE comprises at least one of rejecting a registration ofthe UE with a serving network, logging an event corresponding to theconcealed subscription identifier not corresponding to the permanentsubscription identifier, notifying a law enforcement organization, andnotifying the UE.

Embodiment 19. The network device of any of embodiments 16-18, whereinthe concealed subscription identifier comprises a SUCI that iscalculated by the UE based on information provided by the HN.

Embodiment 20. The network device of any of embodiments 16-18, whereinthe permanent subscription identifier comprises a SUPI.

Embodiment 21. The network device of any of embodiments 16-20, whereinthe SUPI comprises an International Mobile Subscription Identifier,IMSI, or a network specific identifier.

Embodiment 22. The network device of any of embodiments 16-21, whereinthe concealed subscription identifier conceals the permanentsubscription identifier.

Embodiment 23. The network device of any of embodiments 16-22, whereinobtaining the concealed subscription identifier comprises obtaining amobile country code, MCC, having a first MCC value and a mobile networkcode, MNC, having a first MNC value,

wherein obtaining the permanent subscription identifier comprisesobtaining the MCC having a second MCC value and the MNC having thesecond MNC value, and

wherein determining that the concealed subscription identifiercorresponds to the permanent subscription identifier comprisesdetermining that the first MCC value equals the second MCC value andthat the first MNC value equals the second MNC value.

Embodiment 24. The network device of embodiment 23, wherein performingthe subscription binding comprises performing the subscription bindingusing the second MCC value and the second MNC value.

Embodiment 25. The network device of embodiment 23, wherein performingthe subscription binding comprises performing the subscription bindingusing the second MCC value and the second MNC value.

Embodiment 26. The network device of any of embodiments 24-25, furthercomprising determining if a SUPI type is received from the UE and theHN.

Embodiment 27. The network device of embodiment 26, wherein theconcealed subscription identifier comprises a first type and thepermanent subscription identifier comprises a second type that isdifferent from the first type.

Embodiment 28. The network device of embodiment 27, wherein thedetermining that the concealed subscription identifier corresponds tothe permanent subscription identifier comprises determining that thefirst MCC value in the first type equals the second MCC value in thesecond type and that the first MNC value in the first type equals thesecond MNC value in the second type.

Embodiment 29. The network device of any of embodiments 16-28, furthercomprising transmitting the concealed subscription identifier that isreceived from the UE to the HN.

Embodiment 30. A method of operating a mobile terminal for providingregulation compliant privacy in a communications network, the methodcomprising:

transmitting a concealed subscription identifier to a service network,the concealed subscription identifier comprising at least a first homenetwork identifier; and

using a SUPI with at least the first home network identifier in binding.

Embodiment 31. The method of embodiment 30, wherein the concealedsubscription identifier comprises a first MCC value and a first MNCvalue.

Embodiment 32. The method of embodiment 30, wherein the concealedsubscription identifier conceals a permanent subscription identifier.

Embodiment 33. The method of embodiment 32, wherein the concealedsubscription identifier comprises an IMSI type.

Embodiment 34. The method of embodiment 32, wherein the concealedsubscription identifier comprises a network access identifier, NAI.

Embodiment 35. The method of embodiment 32, wherein the mobile terminaluses the permanent subscription identifier that is concealed in theconcealed subscription identifier to perform a SUPI binding.

Embodiment 36. A mobile terminal comprising:

at least one processor;

at least one memory connected to the at least one processor and storingprogram code that is executed by the at least one processor to performoperations comprising:

transmitting a concealed subscription identifier to a service network,the concealed subscription identifier comprising at least a first homenetwork identifier; and

using a SUPI with at least the first home network identifier in binding.

Embodiment 37. The mobile terminal of embodiment 36, wherein theconcealed subscription identifier comprises a first MCC value and afirst MNC value.

Embodiment 38. The mobile terminal of embodiment 36, wherein theconcealed subscription identifier conceals a permanent subscriptionidentifier.

Embodiment 39. The mobile terminal of embodiment 38, wherein theconcealed subscription identifier comprises an IMSI type.

Embodiment 40. The mobile terminal of embodiment 38, wherein theconcealed subscription identifier comprises a network access identifier,NAI.

Embodiment 41. The mobile terminal of embodiment 38, wherein the mobileterminal uses the permanent subscription identifier that is concealed inthe concealed subscription identifier to perform a SUPI binding.

Embodiment 42. A computer program product comprising:

a non-transitory computer readable medium storing program codeconfigured for execution by a processor of a network device to cause theprocessor to perform operations for providing regulation compliantprivacy in a communications network according to embodiments 30-35.

Embodiment 43. A computer program for providing regulation compliantprivacy in a communications network that, when executed, performsoperations according to embodiments 30-35.

Further Definitions and Embodiments are Discussed Below

In the above-description of various embodiments of present inventiveconcepts, it is to be understood that the terminology used herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of present inventive concepts. Unless otherwisedefined, all terms (including technical and scientific terms) usedherein have the same meaning as commonly understood by one of ordinaryskill in the art to which present inventive concepts belong. It will befurther understood that terms, such as those defined in commonly useddictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of this specification andthe relevant art and will not be interpreted in an idealized or overlyformal sense unless expressly so defined herein.

When an element is referred to as being “connected”, “coupled”,“responsive”, or variants thereof to another element, it can be directlyconnected, coupled, or responsive to the other element or interveningelements may be present. In contrast, when an element is referred to asbeing “directly connected”, “directly coupled”, “directly responsive”,or variants thereof to another element, there are no interveningelements present. Like numbers refer to like elements throughout.Furthermore, “coupled”, “connected”, “responsive”, or variants thereofas used herein may include wirelessly coupled, connected, or responsive.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Well-known functions or constructions may not be described indetail for brevity and/or clarity. The term “and/or” includes any andall combinations of one or more of the associated listed items.

It will be understood that although the terms first, second, third, etc.may be used herein to describe various elements/operations, theseelements/operations should not be limited by these terms. These termsare only used to distinguish one element/operation from anotherelement/operation. Thus a first element/operation in some embodimentscould be termed a second element/operation in other embodiments withoutdeparting from the teachings of present inventive concepts. The samereference numerals or the same reference designators denote the same orsimilar elements throughout the specification.

As used herein, the terms “comprise”, “comprising”, “comprises”,“include”, “including”, “includes”, “have”, “has”, “having”, or variantsthereof are open-ended, and include one or more stated features,integers, elements, steps, components or functions but does not precludethe presence or addition of one or more other features, integers,elements, steps, components, functions or groups thereof. Furthermore,as used herein, the common abbreviation “e.g.”, which derives from theLatin phrase “exempli gratia,” may be used to introduce or specify ageneral example or examples of a previously mentioned item, and is notintended to be limiting of such item. The common abbreviation “i.e.”,which derives from the Latin phrase “id est,” may be used to specify aparticular item from a more general recitation.

Example embodiments are described herein with reference to blockdiagrams and/or flowchart illustrations of computer-implemented methods,apparatus (systems and/or devices) and/or computer program products. Itis understood that a block of the block diagrams and/or flowchartillustrations, and combinations of blocks in the block diagrams and/orflowchart illustrations, can be implemented by computer programinstructions that are performed by one or more computer circuits. Thesecomputer program instructions may be provided to a processor circuit ofa general purpose computer circuit, special purpose computer circuit,and/or other programmable data processing circuit to produce a machine,such that the instructions, which execute via the processor of thecomputer and/or other programmable data processing apparatus, transformand control transistors, values stored in memory locations, and otherhardware components within such circuitry to implement thefunctions/acts specified in the block diagrams and/or flowchart block orblocks, and thereby create means (functionality) and/or structure forimplementing the functions/acts specified in the block diagrams and/orflowchart block(s).

These computer program instructions may also be stored in a tangiblecomputer-readable medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instructions whichimplement the functions/acts specified in the block diagrams and/orflowchart block or blocks. Accordingly, embodiments of present inventiveconcepts may be embodied in hardware and/or in software (includingfirmware, resident software, micro-code, etc.) that runs on a processorsuch as a digital signal processor, which may collectively be referredto as “circuitry,” “a module” or variants thereof.

It should also be noted that in some alternate implementations, thefunctions/acts noted in the blocks may occur out of the order noted inthe flowcharts. For example, two blocks shown in succession may in factbe executed substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending upon the functionality/actsinvolved. Moreover, the functionality of a given block of the flowchartsand/or block diagrams may be separated into multiple blocks and/or thefunctionality of two or more blocks of the flowcharts and/or blockdiagrams may be at least partially integrated. Finally, other blocks maybe added/inserted between the blocks that are illustrated, and/orblocks/operations may be omitted without departing from the scope ofinventive concepts. Moreover, although some of the diagrams includearrows on communication paths to show a primary direction ofcommunication, it is to be understood that communication may occur inthe opposite direction to the depicted arrows.

Many variations and modifications can be made to the embodiments withoutsubstantially departing from the principles of the present inventiveconcepts. All such variations and modifications are intended to beincluded herein within the scope of present inventive concepts.Accordingly, the above disclosed subject matter is to be consideredillustrative, and not restrictive, and the examples of embodiments areintended to cover all such modifications, enhancements, and otherembodiments, which fall within the spirit and scope of present inventiveconcepts. Thus, to the maximum extent allowed by law, the scope ofpresent inventive concepts are to be determined by the broadestpermissible interpretation of the present disclosure including theexamples of embodiments and their equivalents, and shall not berestricted or limited by the foregoing detailed description.

Additional Explanation is Provided Below.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art.

FIG. 10: A wireless network in accordance with some embodiments.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 10.For simplicity, the wireless network of FIG. 10 only depicts networkQQ106, network nodes QQ160 and QQ160 b, and WDs QQ110, QQ110 b, andQQ110 c (also referred to as mobile terminals). In practice, a wirelessnetwork may further include any additional elements suitable to supportcommunication between wireless devices or between a wireless device andanother communication device, such as a landline telephone, a serviceprovider, or any other network node or end device. Of the illustratedcomponents, network node QQ160 and wireless device (WD) QQ110 aredepicted with additional detail. The wireless network may providecommunication and other types of services to one or more wirelessdevices to facilitate the wireless devices' access to and/or use of theservices provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network QQ106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node QQ160 and WD QQ110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 10, network node QQ160 includes processing circuitry QQ170,device readable medium QQ180, interface QQ190, auxiliary equipmentQQ184, power source QQ186, power circuitry QQ187, and antenna QQ162.Although network node QQ160 illustrated in the example wireless networkof FIG. 10 may represent a device that includes the illustratedcombination of hardware components, other embodiments may comprisenetwork nodes with different combinations of components. It is to beunderstood that a network node comprises any suitable combination ofhardware and/or software needed to perform the tasks, features,functions and methods disclosed herein. Moreover, while the componentsof network node QQ160 are depicted as single boxes located within alarger box, or nested within multiple boxes, in practice, a network nodemay comprise multiple different physical components that make up asingle illustrated component (e.g., device readable medium QQ180 maycomprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node QQ160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node QQ160 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium QQ180 for thedifferent RATs) and some components may be reused (e.g., the sameantenna QQ162 may be shared by the RATs). Network node QQ160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node QQ160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node QQ160.

Processing circuitry QQ170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry QQ170 may include processinginformation obtained by processing circuitry QQ170 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry QQ170 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode QQ160 components, such as device readable medium QQ180, networknode QQ160 functionality. For example, processing circuitry QQ170 mayexecute instructions stored in device readable medium QQ180 or in memorywithin processing circuitry QQ170. Such functionality may includeproviding any of the various wireless features, functions, or benefitsdiscussed herein. In some embodiments, processing circuitry QQ170 mayinclude a system on a chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or moreof radio frequency (RF) transceiver circuitry QQ172 and basebandprocessing circuitry QQ174. In some embodiments, radio frequency (RF)transceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry QQ170executing instructions stored on device readable medium QQ180 or memorywithin processing circuitry QQ170. In alternative embodiments, some orall of the functionality may be provided by processing circuitry QQ170without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry QQ170 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry QQ170 alone or toother components of network node QQ160, but are enjoyed by network nodeQQ160 as a whole, and/or by end users and the wireless networkgenerally.

Device readable medium QQ180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry QQ170. Device readable medium QQ180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ170 and, utilized by network node QQ160.Device readable medium QQ180 may be used to store any calculations madeby processing circuitry QQ170 and/or any data received via interfaceQQ190. In some embodiments, processing circuitry QQ170 and devicereadable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication ofsignalling and/or data between network node QQ160, network QQ106, and/orWDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s)QQ194 to send and receive data, for example to and from network QQ106over a wired connection. Interface QQ190 also includes radio front endcircuitry QQ192 that may be coupled to, or in certain embodiments a partof, antenna QQ162. Radio front end circuitry QQ192 comprises filtersQQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may beconnected to antenna QQ162 and processing circuitry QQ170. Radio frontend circuitry may be configured to condition signals communicatedbetween antenna QQ162 and processing circuitry QQ170. Radio front endcircuitry QQ192 may receive digital data that is to be sent out to othernetwork nodes or WDs via a wireless connection. Radio front endcircuitry QQ192 may convert the digital data into a radio signal havingthe appropriate channel and bandwidth parameters using a combination offilters QQ198 and/or amplifiers QQ196. The radio signal may then betransmitted via antenna QQ162. Similarly, when obtaining data, antennaQQ162 may collect radio signals which are then converted into digitaldata by radio front end circuitry QQ192. The digital data may be passedto processing circuitry QQ170. In other embodiments, the interface maycomprise different components and/or different combinations ofcomponents.

In certain alternative embodiments, network node QQ160 may not includeseparate radio front end circuitry QQ192, instead, processing circuitryQQ170 may comprise radio front end circuitry and may be connected toantenna QQ162 without separate radio front end circuitry QQ192.Similarly, in some embodiments, all or some of RF transceiver circuitryQQ172 may be considered a part of interface QQ190. In still otherembodiments, interface QQ190 may include one or more ports or terminalsQQ194, radio front end circuitry QQ192, and RF transceiver circuitryQQ172, as part of a radio unit (not shown), and interface QQ190 maycommunicate with baseband processing circuitry QQ174, which is part of adigital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna QQ162 may becoupled to radio front end circuitry QQ190 and may be any type ofantenna capable of transmitting and obtaining data and/or signalswirelessly. In some embodiments, antenna QQ162 may comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna may be used to transmit/receive radio signalsin any direction, a sector antenna may be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna maybe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna may be referred to as MIMO. In certain embodiments, antennaQQ162 may be separate from network node QQ160 and may be connectable tonetwork node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any obtaining operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry QQ187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network nodeQQ160 with power for performing the functionality described herein.Power circuitry QQ187 may receive power from power source QQ186. Powersource QQ186 and/or power circuitry QQ187 may be configured to providepower to the various components of network node QQ160 in a form suitablefor the respective components (e.g., at a voltage and current levelneeded for each respective component). Power source QQ186 may either beincluded in, or external to, power circuitry QQ187 and/or network nodeQQ160. For example, network node QQ160 may be connectable to an externalpower source (e.g., an electricity outlet) via an input circuitry orinterface such as an electrical cable, whereby the external power sourcesupplies power to power circuitry QQ187. As a further example, powersource QQ186 may comprise a source of power in the form of a battery orbattery pack which is connected to, or integrated in, power circuitryQQ187. The battery may provide backup power should the external powersource fail. Other types of power sources, such as photovoltaic devices,may also be used.

Alternative embodiments of network node QQ160 may include additionalcomponents beyond those shown in FIG. 10 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node QQ160 may include user interface equipment to allow inputof information into network node QQ160 and to allow output ofinformation from network node QQ160. This may allow a user to performdiagnostic, maintenance, repair, and other administrative functions fornetwork node QQ160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE) andother types of a mobile terminal. Communicating wirelessly may involvetransmitting and/or obtaining wireless signals using electromagneticwaves, radio waves, infrared waves, and/or other types of signalssuitable for conveying information through air. In some embodiments, aWD may be configured to transmit and/or receive information withoutdirect human interaction. For instance, a WD may be designed to transmitinformation to a network on a predetermined schedule, when triggered byan internal or external event, or in response to requests from thenetwork. Examples of a WD include, but are not limited to, a smartphone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, awireless local loop phone, a desktop computer, a personal digitalassistant (PDA), a wireless cameras, a gaming console or device, a musicstorage device, a playback appliance, a wearable terminal device, awireless endpoint, a mobile station, a tablet, a laptop, alaptop-embedded equipment (LEE), a laptop-mounted equipment (LME), asmart device, a wireless customer-premise equipment (CPE). avehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V21), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device. As yet anotherspecific example, in an Internet of Things (IoT) scenario, a WD mayrepresent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a machine-to-machine (M2M) device, which may in a 3GPP contextbe referred to as an MTC device. As one particular example, the WD maybe a UE or other terminal implementing the 3GPP narrow band internet ofthings (NB-IoT) standard. Particular examples of such machines ordevices are sensors, metering devices such as power meters, industrialmachinery, or home or personal appliances (e.g. refrigerators,televisions, etc.) personal wearables (e.g., watches, fitness trackers,etc.). In other scenarios, a WD may represent a vehicle or otherequipment that is capable of monitoring and/or reporting on itsoperational status or other functions associated with its operation. AWD as described above may represent the endpoint of a wirelessconnection, in which case the device may be referred to as a wirelessterminal. Furthermore, a WD as described above may be mobile, in whichcase it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device QQ110 includes antenna QQ111, interfaceQQ114, processing circuitry QQ120, device readable medium QQ130, userinterface equipment QQ132, auxiliary equipment QQ134, power source QQ136and power circuitry QQ137. WD QQ110 may include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies may be integrated into the same or different chipsor set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface QQ114. In certain alternative embodiments, antenna QQ111 maybe separate from WD QQ110 and be connectable to WD QQ110 through aninterface or port. Antenna QQ111, interface QQ114, and/or processingcircuitry QQ120 may be configured to perform any obtaining ortransmitting operations described herein as being performed by a WD. Anyinformation, data and/or signals may be received from a network nodeand/or another WD. In some embodiments, radio front end circuitry and/orantenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitryQQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one ormore filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114is connected to antenna QQ111 and processing circuitry QQ120, and isconfigured to condition signals communicated between antenna QQ111 andprocessing circuitry QQ120. Radio front end circuitry QQ112 may becoupled to or a part of antenna QQ111. In some embodiments, WD QQ110 maynot include separate radio front end circuitry QQ112; rather, processingcircuitry QQ120 may comprise radio front end circuitry and may beconnected to antenna QQ111. Similarly, in some embodiments, some or allof RF transceiver circuitry QQ122 may be considered a part of interfaceQQ114. Radio front end circuitry QQ112 may receive digital data that isto be sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry QQ112 may convert the digital data into aradio signal having the appropriate channel and bandwidth parametersusing a combination of filters QQ118 and/or amplifiers QQ116. The radiosignal may then be transmitted via antenna QQ111. Similarly, whenobtaining data, antenna QQ111 may collect radio signals which are thenconverted into digital data by radio front end circuitry QQ112. Thedigital data may be passed to processing circuitry QQ120. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

Processing circuitry QQ120 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD QQ110components, such as device readable medium QQ130, WD QQ110functionality. Such functionality may include providing any of thevarious wireless features or benefits discussed herein. For example,processing circuitry QQ120 may execute instructions stored in devicereadable medium QQ130 or in memory within processing circuitry QQ120 toprovide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitryQQ120 of WD QQ110 may comprise a SOC. In some embodiments, RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be on separate chips or setsof chips. In alternative embodiments, part or all of baseband processingcircuitry QQ124 and application processing circuitry QQ126 may becombined into one chip or set of chips, and RF transceiver circuitryQQ122 may be on a separate chip or set of chips. In still alternativeembodiments, part or all of RF transceiver circuitry QQ122 and basebandprocessing circuitry QQ124 may be on the same chip or set of chips, andapplication processing circuitry QQ126 may be on a separate chip or setof chips. In yet other alternative embodiments, part or all of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be combined in the same chipor set of chips. In some embodiments, RF transceiver circuitry QQ122 maybe a part of interface QQ114. RF transceiver circuitry QQ122 maycondition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry QQ120 executing instructions stored on device readable mediumQQ130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry QQ120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry QQ120 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry QQ120 alone or to other componentsof WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end usersand the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry QQ120, may include processinginformation obtained by processing circuitry QQ120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD QQ110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium QQ130 may be operable to store a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ120. Device readable medium QQ130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry QQ120. In someembodiments, processing circuitry QQ120 and device readable medium QQ130may be considered to be integrated. User interface equipment QQ132 mayprovide components that allow for a human user to interact with WDQQ110. Such interaction may be of many forms, such as visual, audial,tactile, etc. User interface equipment QQ132 may be operable to produceoutput to the user and to allow the user to provide input to WD QQ110.The type of interaction may vary depending on the type of user interfaceequipment QQ132 installed in WD QQ110. For example, if WD QQ110 is asmart phone, the interaction may be via a touch screen; if WD QQ110 is asmart meter, the interaction may be through a screen that provides usage(e.g., the number of gallons used) or a speaker that provides an audiblealert (e.g., if smoke is detected). User interface equipment QQ132 mayinclude input interfaces, devices and circuits, and output interfaces,devices and circuits. User interface equipment QQ132 is configured toallow input of information into WD QQ110, and is connected to processingcircuitry QQ120 to allow processing circuitry QQ120 to process the inputinformation. User interface equipment QQ132 may include, for example, amicrophone, a proximity or other sensor, keys/buttons, a touch display,one or more cameras, a USB port, or other input circuitry. Userinterface equipment QQ132 is also configured to allow output ofinformation from WD QQ110, and to allow processing circuitry QQ120 tooutput information from WD QQ110. User interface equipment QQ132 mayinclude, for example, a speaker, a display, vibrating circuitry, a USBport, a headphone interface, or other output circuitry. Using one ormore input and output interfaces, devices, and circuits, of userinterface equipment QQ132, WD QQ110 may communicate with end usersand/or the wireless network, and allow them to benefit from thefunctionality described herein.

Auxiliary equipment QQ134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD QQ110 may further comprise power circuitryQQ137 for delivering power from power source QQ136 to the various partsof WD QQ110 which need power from power source QQ136 to carry out anyfunctionality described or indicated herein. Power circuitry QQ137 mayin certain embodiments comprise power management circuitry. Powercircuitry QQ137 may additionally or alternatively be operable to receivepower from an external power source; in which case WD QQ110 may beconnectable to the external power source (such as an electricity outlet)via input circuitry or an interface such as an electrical power cable.Power circuitry QQ137 may also in certain embodiments be operable todeliver power from an external power source to power source QQ136. Thismay be, for example, for the charging of power source QQ136. Powercircuitry QQ137 may perform any formatting, converting, or othermodification to the power from power source QQ136 to make the powersuitable for the respective components of WD QQ110 to which power issupplied.

FIG. 11: User Equipment in accordance with some embodiments

FIG. 11 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE QQ2200 may be any UE identifiedby the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE,a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.UE QQ200, as illustrated in FIG. 11, is one example of a WD configuredfor communication in accordance with one or more communication standardspromulgated by the 3rd Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE may be used interchangeable. Accordingly, although FIG.11 is a UE, the components discussed herein are equally applicable to aWD, and vice-versa.

In FIG. 11, UE QQ200 includes processing circuitry QQ201 that isoperatively coupled to input/output interface QQ205, radio frequency(RF) interface QQ209, network connection interface QQ211, memory QQ215including random access memory (RAM) QQ217, read-only memory (ROM)QQ219, and storage medium QQ221 or the like, communication subsystemQQ231, power source QQ233, and/or any other component, or anycombination thereof. Storage medium QQ221 includes operating systemQQ223, application program QQ225, and data QQ227. In other embodiments,storage medium QQ221 may include other similar types of information.Certain UEs may utilize all of the components shown in FIG. 11, or onlya subset of the components. The level of integration between thecomponents may vary from one UE to another UE. Further, certain UEs maycontain multiple instances of a component, such as multiple processors,memories, transceivers, transmitters, receivers, etc.

In FIG. 11, processing circuitry QQ201 may be configured to processcomputer instructions and data. Processing circuitry QQ201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry QQ201 may includetwo central processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface QQ205 may beconfigured to provide a communication interface to an input device,output device, or input and output device. UE QQ200 may be configured touse an output device via input/output interface QQ205. An output devicemay use the same type of interface port as an input device. For example,a USB port may be used to provide input to and output from UE QQ200. Theoutput device may be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE QQ200 may be configured to use aninput device via input/output interface QQ205 to allow a user to captureinformation into UE QQ200. The input device may include atouch-sensitive or presence-sensitive display, a camera (e.g., a digitalcamera, a digital video camera, a web camera, etc.), a microphone, asensor, a mouse, a trackball, a directional pad, a trackpad, a scrollwheel, a smartcard, and the like. The presence-sensitive display mayinclude a capacitive or resistive touch sensor to sense input from auser. A sensor may be, for instance, an accelerometer, a gyroscope, atilt sensor, a force sensor, a magnetometer, an optical sensor, aproximity sensor, another like sensor, or any combination thereof. Forexample, the input device may be an accelerometer, a magnetometer, adigital camera, a microphone, and an optical sensor.

In FIG. 11, RF interface QQ209 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface QQ211 may beconfigured to provide a communication interface to network QQ243 a.Network QQ243 a may encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network QQ243 a may comprise aWi-Fi network. Network connection interface QQ211 may be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface QQ211 may implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions may share circuit components, software or firmware,or alternatively may be implemented separately.

RAM QQ217 may be configured to interface via bus QQ202 to processingcircuitry QQ201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM QQ219may be configured to provide computer instructions or data to processingcircuitry QQ201. For example, ROM QQ219 may be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage mediumQQ221 may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium QQ221 may be configured toinclude operating system QQ223, application program QQ225 such as a webbrowser application, a widget or gadget engine or another application,and data file QQ227. Storage medium QQ221 may store, for use by UEQQ200, any of a variety of various operating systems or combinations ofoperating systems.

Storage medium QQ221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium QQ221 may allow UE QQ200 to access computer-executableinstructions, application programs or the like, stored on transitory ornon-transitory memory media, to off-load data, or to upload data. Anarticle of manufacture, such as one utilizing a communication system maybe tangibly embodied in storage medium QQ221, which may comprise adevice readable medium.

In FIG. 11, processing circuitry QQ201 may be configured to communicatewith network QQ243 b using communication subsystem QQ231. Network QQ243a and network QQ243 b may be the same network or networks or differentnetwork or networks. Communication subsystem QQ231 may be configured toinclude one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.QQ2,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter QQ233 and/or receiver QQ235 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter QQ233and receiver QQ235 of each transceiver may share circuit components,software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem QQ231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem QQ231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network QQ243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, networkQQ243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source QQ213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE QQ200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE QQ200 or partitioned acrossmultiple components of UE QQ200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystemQQ231 may be configured to include any of the components describedherein. Further, processing circuitry QQ201 may be configured tocommunicate with any of such components over bus QQ202. In anotherexample, any of such components may be represented by programinstructions stored in memory that when executed by processing circuitryQQ201 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components may be partitionedbetween processing circuitry QQ201 and communication subsystem QQ231. Inanother example, the non-computationally intensive functions of any ofsuch components may be implemented in software or firmware and thecomputationally intensive functions may be implemented in hardware.

FIG. 12: Virtualization environment in accordance with some embodiments

FIG. 12 is a schematic block diagram illustrating a virtualizationenvironment QQ300 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments QQ300 hosted byone or more of hardware nodes QQ330. Further, in embodiments in whichthe virtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications QQ320(which may alternatively be called software instances, virtualappliances, network functions, virtual nodes, virtual network functions,etc.) operative to implement some of the features, functions, and/orbenefits of some of the embodiments disclosed herein. Applications QQ320are run in virtualization environment QQ300 which provides hardwareQQ330 comprising processing circuitry QQ360 and memory QQ390. MemoryQQ390 contains instructions QQ395 executable by processing circuitryQQ360 whereby application QQ320 is operative to provide one or more ofthe features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose orspecial-purpose network hardware devices QQ330 comprising a set of oneor more processors or processing circuitry QQ360, which may becommercial off-the-shelf (COTS) processors, dedicated ApplicationSpecific Integrated Circuits (ASICs), or any other type of processingcircuitry including digital or analog hardware components or specialpurpose processors. Each hardware device may comprise memory QQ390-1which may be non-persistent memory for temporarily storing instructionsQQ395 or software executed by processing circuitry QQ360. Each hardwaredevice may comprise one or more network interface controllers (NICs)QQ370, also known as network interface cards, which include physicalnetwork interface QQ380. Each hardware device may also includenon-transitory, persistent, machine-readable storage media QQ390-2having stored therein software QQ395 and/or instructions executable byprocessing circuitry QQ360. Software QQ395 may include any type ofsoftware including software for instantiating one or more virtualizationlayers QQ350 (also referred to as hypervisors), software to executevirtual machines QQ340 as well as software allowing it to executefunctions, features and/or benefits described in relation with someembodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer QQ350 or hypervisor. Differentembodiments of the instance of virtual appliance QQ320 may beimplemented on one or more of virtual machines QQ340, and theimplementations may be made in different ways.

During operation, processing circuitry QQ360 executes software QQ395 toinstantiate the hypervisor or virtualization layer QQ350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer QQ350 may present a virtual operating platform thatappears like networking hardware to virtual machine QQ340.

As shown in FIG. 12, hardware QQ330 may be a standalone network nodewith generic or specific components. Hardware QQ330 may comprise antennaQQ3225 and may implement some functions via virtualization.Alternatively, hardware QQ330 may be part of a larger cluster ofhardware (e.g. such as in a data center or customer premise equipment(CPE)) where many hardware nodes work together and are managed viamanagement and orchestration (MANO) QQ3100, which, among others,oversees lifecycle management of applications QQ320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine QQ340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines QQ340, and that part of hardware QQ330 that executes thatvirtual machine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines QQ340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines QQ340 on top of hardware networking infrastructureQQ330 and corresponds to application QQ320 in FIG. 12.

In some embodiments, one or more radio units QQ3200 that each includeone or more transmitters QQ3220 and one or more receivers QQ3210 may becoupled to one or more antennas QQ3225. Radio units QQ3200 maycommunicate directly with hardware nodes QQ330 via one or moreappropriate network interfaces and may be used in combination with thevirtual components to provide a virtual node with radio capabilities,such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use ofcontrol system QQ3230 which may alternatively be used for communicationbetween the hardware nodes QQ330 and radio units QQ3200.

FIG. 13: Telecommunication network connected via an intermediate networkto a host computer in accordance with some embodiments.

With reference to FIG. 13, in accordance with an embodiment, acommunication system includes telecommunication network QQ410, such as a3GPP-type cellular network, which comprises access network QQ411, suchas a radio access network, and core network QQ414. Access network QQ411comprises a plurality of base stations QQ412 a, QQ412 b, QQ412 c, suchas NBs, eNBs, gNBs or other types of wireless access points, eachdefining a corresponding coverage area QQ413 a, QQ413 b, QQ413 c. Eachbase station QQ412 a, QQ412 b, QQ412 c is connectable to core networkQQ414 over a wired or wireless connection QQ415. A first UE QQ491located in coverage area QQ413 c is configured to wirelessly connect to,or be paged by, the corresponding base station QQ412 c. A second UEQQ492 in coverage area QQ413 a is wirelessly connectable to thecorresponding base station QQ412 a. While a plurality of UEs QQ491,QQ492 are illustrated in this example, the disclosed embodiments areequally applicable to a situation where a sole UE is in the coveragearea or where a sole UE is connecting to the corresponding base stationQQ412.

Telecommunication network QQ410 is itself connected to host computerQQ430, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer QQ430 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections QQ421 and QQ422 between telecommunication network QQ410 andhost computer QQ430 may extend directly from core network QQ414 to hostcomputer QQ430 or may go via an optional intermediate network QQ420.Intermediate network QQ420 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network QQ420,if any, may be a backbone network or the Internet; in particular,intermediate network QQ420 may comprise two or more sub-networks (notshown).

The communication system of FIG. 13 as a whole enables connectivitybetween the connected UEs QQ491, QQ492 and host computer QQ430. Theconnectivity may be described as an over-the-top (OTT) connection QQ450.Host computer QQ430 and the connected UEs QQ491, QQ492 are configured tocommunicate data and/or signaling via OTT connection QQ450, using accessnetwork QQ411, core network QQ414, any intermediate network QQ420 andpossible further infrastructure (not shown) as intermediaries. OTTconnection QQ450 may be transparent in the sense that the participatingcommunication devices through which OTT connection QQ450 passes areunaware of routing of uplink and downlink communications. For example,base station QQ412 may not or need not be informed about the pastrouting of an incoming downlink communication with data originating fromhost computer QQ430 to be forwarded (e.g., handed over) to a connectedUE QQ491. Similarly, base station QQ412 need not be aware of the futurerouting of an outgoing uplink communication originating from the UEQQ491 towards the host computer QQ430.

FIG. 14: Host computer communicating via a base station with a userequipment over a partially wireless connection in accordance with someembodiments.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 14. In communication systemQQ500, host computer QQ510 comprises hardware QQ515 includingcommunication interface QQ516 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of communication system QQ500. Host computer QQ510 furthercomprises processing circuitry QQ518, which may have storage and/orprocessing capabilities. In particular, processing circuitry QQ518 maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer QQ510further comprises software QQ511, which is stored in or accessible byhost computer QQ510 and executable by processing circuitry QQ518.Software QQ511 includes host application QQ512. Host application QQ512may be operable to provide a service to a remote user, such as UE QQ530connecting via OTT connection QQ550 terminating at UE QQ530 and hostcomputer QQ510. In providing the service to the remote user, hostapplication QQ512 may provide user data which is transmitted using OTTconnection QQ550.

Communication system QQ500 further includes base station QQ520 providedin a telecommunication system and comprising hardware QQ525 enabling itto communicate with host computer QQ510 and with UE QQ530. HardwareQQ525 may include communication interface QQ526 for setting up andmaintaining a wired or wireless connection with an interface of adifferent communication device of communication system QQ500, as well asradio interface QQ527 for setting up and maintaining at least wirelessconnection QQ570 with UE QQ530 located in a coverage area (not shown inFIG. 14) served by base station QQ520. Communication interface QQ526 maybe configured to facilitate connection QQ560 to host computer QQ510.Connection QQ560 may be direct or it may pass through a core network(not shown in FIG. 14) of the telecommunication system and/or throughone or more intermediate networks outside the telecommunication system.In the embodiment shown, hardware QQ525 of base station QQ520 furtherincludes processing circuitry QQ528, which may comprise one or moreprogrammable processors, application-specific integrated circuits, fieldprogrammable gate arrays or combinations of these (not shown) adapted toexecute instructions. Base station QQ520 further has software QQ521stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referredto. Its hardware QQ535 may include radio interface QQ537 configured toset up and maintain wireless connection QQ570 with a base stationserving a coverage area in which UE QQ530 is currently located. HardwareQQ535 of UE QQ530 further includes processing circuitry QQ538, which maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. UE QQ530 furthercomprises software QQ531, which is stored in or accessible by UE QQ530and executable by processing circuitry QQ538. Software QQ531 includesclient application QQ532. Client application QQ532 may be operable toprovide a service to a human or non-human user via UE QQ530, with thesupport of host computer QQ510. In host computer QQ510, an executinghost application QQ512 may communicate with the executing clientapplication QQ532 via OTT connection QQ550 terminating at UE QQ530 andhost computer QQ510. In providing the service to the user, clientapplication QQ532 may receive request data from host application QQ512and provide user data in response to the request data. OTT connectionQQ550 may transfer both the request data and the user data. Clientapplication QQ532 may interact with the user to generate the user datathat it provides.

It is noted that host computer QQ510, base station QQ520 and UE QQ530illustrated in FIG. 14 may be similar or identical to host computerQQ430, one of base stations QQ412 a, QQ412 b, QQ412 c and one of UEsQQ491, QQ492 of FIG. 13, respectively. This is to say, the innerworkings of these entities may be as shown in FIG. 14 and independently,the surrounding network topology may be that of FIG. 13.

In FIG. 14, OTT connection QQ550 has been drawn abstractly to illustratethe communication between host computer QQ510 and UE QQ530 via basestation QQ520, without explicit reference to any intermediary devicesand the precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE QQ530 or from the service provider operating host computerQQ510, or both. While OTT connection QQ550 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments may improve theperformance of OTT services provided to UE QQ530 using OTT connectionQQ550, in which wireless connection QQ570 forms the last segment. Moreprecisely, the teachings of these embodiments may improve the deblockfiltering for video processing and thereby provide benefits such asimproved video encoding and/or decoding.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection QQ550 between hostcomputer QQ510 and UE QQ530, in response to variations in themeasurement results. The measurement procedure and/or the networkfunctionality for reconfiguring OTT connection QQ550 may be implementedin software QQ511 and hardware QQ515 of host computer QQ510 or insoftware QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments,sensors (not shown) may be deployed in or in association withcommunication devices through which OTT connection QQ550 passes; thesensors may participate in the measurement procedure by supplying valuesof the monitored quantities exemplified above, or supplying values ofother physical quantities from which software QQ511, QQ531 may computeor estimate the monitored quantities. The reconfiguring of OTTconnection QQ550 may include message format, retransmission settings,preferred routing etc.; the reconfiguring need not affect base stationQQ520, and it may be unknown or imperceptible to base station QQ520.Such procedures and functionalities may be known and practiced in theart. In certain embodiments, measurements may involve proprietary UEsignaling facilitating host computer QQ510's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software QQ511 and QQ531 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection QQ550 while it monitors propagation times, errors etc.

FIG. 15: Methods implemented in a communication system including a hostcomputer, a base station and a user equipment in accordance with someembodiments.

FIG. 15 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to Figures QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG. 15will be included in this section. In step QQ610, the host computerprovides user data. In substep QQ611 (which may be optional) of stepQQ610, the host computer provides the user data by executing a hostapplication. In step QQ620, the host computer initiates a transmissioncarrying the user data to the UE. In step QQ630 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step QQ640 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 16: Methods implemented in a communication system including a hostcomputer, a base station and a user equipment in accordance with someembodiments.

FIG. 16 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to Figures QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG. 16will be included in this section. In step QQ710 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In stepQQ720, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step QQ730 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 17: Methods implemented in a communication system including a hostcomputer, a base station and a user equipment in accordance with someembodiments.

FIG. 17 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to Figures QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG. 17will be included in this section. In step QQ810 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step QQ820, the UE provides user data. In substepQQ821 (which may be optional) of step QQ820, the UE provides the userdata by executing a client application. In substep QQ811 (which may beoptional) of step QQ810, the UE executes a client application whichprovides the user data in reaction to the received input data providedby the host computer. In providing the user data, the executed clientapplication may further consider user input received from the user.Regardless of the specific manner in which the user data was provided,the UE initiates, in substep QQ830 (which may be optional), transmissionof the user data to the host computer. In step QQ840 of the method, thehost computer receives the user data transmitted from the UE, inaccordance with the teachings of the embodiments described throughoutthis disclosure.

FIG. 18: Methods implemented in a communication system including a hostcomputer, a base station and a user equipment in accordance with someembodiments.

FIG. 18 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to Figures QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG. 18will be included in this section. In step QQ910 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep QQ920 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In stepQQ930 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

Claims are provided below. Reference numbers/letters are provided inparenthesis by way of example/illustration without limiting exampleembodiments to particular elements indicated by the referencenumbers/letters.

1. A method performed by a network device in a serving network, SN, forproviding regulation compliant privacy in a communications network, themethod comprising: obtaining a concealed subscription identifier from auser equipment, UE, that is associated with a home network, HN;obtaining a permanent subscription identifier that is associated withthe concealed subscription identifier from the HN; determining whetherthe concealed subscription identifier from the UE corresponds to thepermanent subscription identifier from the HN; and responsive todetermining that the concealed subscription identifier from the UEcorresponds to the permanent subscription identifier from the HN,performing further operations to provide service to the UE.
 2. Themethod of claim 1, further comprising, responsive to determining thatthe concealed subscription identifier from the UE does not correspond tothe permanent subscription identifier from the HN, denying service tothe UE.
 3. The method of claim 2, wherein denying the service to the UEcomprises at least one of rejecting a registration of the UE with theSN, logging an event corresponding to the concealed subscriptionidentifier not corresponding to the permanent subscription identifier,notifying a law enforcement organization, and notifying the UE.
 4. Themethod of claim 1, wherein the concealed subscription identifiercomprises a SUCI that is calculated by the UE based on informationprovided by the HN.
 5. The method of claim 1, wherein the permanentsubscription identifier comprises a SUPI.
 6. The method of claim 1,wherein the SUPI comprises an International Mobile SubscriptionIdentifier, IMSI, or a network specific identifier.
 7. The method ofclaim 1, wherein the concealed subscription identifier conceals thepermanent subscription identifier.
 8. The method of claim 1, whereinobtaining the concealed subscription identifier comprises obtaining afirst home network identifier corresponding to the UE having a firstvalue and a second home network identifier corresponding to the HNhaving a second value.
 9. The method of claim 8, wherein obtaining thefirst home network identifier comprises obtaining a mobile country code,MCC, having a first MCC value and a mobile network code, MNC, having afirst MNC value, wherein obtaining the second home network identifiercomprises obtaining an MCC having a second MCC value and the MNC havingthe second MNC value, and wherein determining that the first homenetwork identifier corresponds to the second home network identifiercomprises determining that the first MCC value equals the second MCCvalue and that the first MNC value equals the second MNC value.
 10. Themethod of claim 8, wherein the first home network identifier comprises afirst format and the second home network identifier comprises a secondformat that is different from the first format, and wherein responsiveto determining that the first format and the second format comprise asame realm, operations provide service to the UE.
 11. The method ofclaim 1, wherein obtaining the concealed subscription identifiercomprises obtaining a mobile country code, MCC, having a first MCC valueand a mobile network code, MNC, having a first MNC value, whereinobtaining the permanent subscription identifier comprises obtaining theMCC having a second MCC value and the MNC having the second MNC value,and wherein determining that the concealed subscription identifiercorresponds to the permanent subscription identifier comprisesdetermining that the first MCC value equals the second MCC value andthat the first MNC value equals the second MNC value. 12-21. (canceled)22. The method of claim 1, further comprising transmitting the concealedsubscription identifier that is received from the UE to the HN. 23-24.(canceled)
 25. A network device in a communications network comprising:at least one processor; at least one memory connected to the at leastone processor and storing program code that is executed by the at leastone processor to perform operations comprising: obtaining a concealedsubscription identifier from a user equipment, UE, that is associatedwith a home network, HN; obtaining a permanent subscription identifierthat is associated with the concealed subscription identifier from theHN; determining whether the concealed subscription identifier from theUE corresponds to the permanent subscription identifier from the HN; andresponsive to determining that the concealed subscription identifierfrom the UE corresponds to the permanent subscription identifier fromthe HN, performing further operations to provide service to the UE. 26.(canceled)
 27. A method performed by a mobile terminal for providingregulation compliant privacy in a communications network, the methodcomprising: transmitting a concealed subscription identifier to aservice network, the concealed subscription identifier comprising atleast a first home network identifier; and using a SUPI with at leastthe first home network identifier in binding.
 28. The method of claim27, wherein the concealed subscription identifier comprises a first MCCvalue and a first MNC value.
 29. The method of claim 28, wherein theconcealed subscription identifier conceals a permanent subscriptionidentifier.
 30. The method of claim 27, wherein the concealedsubscription identifier comprises an IMSI type.
 31. The method of claim30, wherein the concealed subscription identifier comprises a networkaccess identifier, NAI.
 32. The method of claim 31, wherein the mobileterminal uses the permanent subscription identifier that is concealed inthe concealed subscription identifier to perform a SUPI binding.
 33. Amobile terminal comprising: at least one processor; at least one memoryconnected to the at least one processor and storing program code that isexecuted by the at least one processor to perform operations comprising:transmitting a concealed subscription identifier to a service network,the concealed subscription identifier comprising at least a first homenetwork identifier; and using a SUPI with at least the first homenetwork identifier in binding. 34-36. (canceled)